Expediting the provisioning of virtual machines based on cached repeated portions of a template

ABSTRACT

A computer-implemented method includes: receiving, by a computing device, a template for creating a virtual machine (VM) instance; separating, by the computing device, the template into a repeated portion and a unique portion; determining, by the computing device, whether the repeated portion is stored in a cache; creating, by the computing device and based on determining that the repeated portion is stored in the cache, the VM instance using the repeated portion stored in the cache; completing, by the computing device, the unique portion of the VM instance to create a completed VM instance; and deploying, by the computing device, the completed VM instance.

BACKGROUND

The present invention generally relates to the provisioning of computingresources and, more particularly, to expediting the provisioning ofvirtual machine resources in clusters based on cached repeated portionsof a template.

Heat Orchestration Template (HOT) is a format or syntax interpretable byan orchestration engine to launch multiple composite cloud applications.HOT may describe an infrastructure pattern and a complete softwarestack. The HOT syntax allows architects to map components to the VirtualMachines (VMs) in which they run and specify the interdependencies amongthose components, and provides a mechanism for passing runtimeattributes between the interdependent components. The HOT syntax can beprovided in a text file and can be treated like computer code. Theorchestration engine in a Heat may use a particular HOT to coordinatethe deployment of virtual machines, network interfaces, and softwarecomponents making sure that the dependencies are honored. The heatservice provides a human- and machine-accessible service for managingthe entire lifecycle of infrastructure and applications within OpenStackclouds. The instantiation of the stack is done with the Heat“stack-create” command. The deployment of the template may be consideredto be successful if the orchestration engine is able to successfullyinstantiate all the resources, which constitute a given stack. Anotherexample for use of templates for provisioning is by using anapplication, such as Docker Compose® for defining and runningmulti-container applications where a compose file is used to configurethe application's services. All the services from this configurationfile can be created and started with a “docker-compose up” command.

As an example, for a stack including an application server cluster(e.g., for a particular application) with a front end load balancer anda backend database, a HOT may describe the installation of anauto-scaling group (or cluster) that will allow the creation of VMinstances with the application and also allow removal of nodes (e.g.,after draining live sessions). When a new node is added to theauto-scaling group, a new VM is deployed with multiple softwaredeployments which, in turn, trigger respective software configurationmanagement instructions and automation tools depending on the action(e.g., create or delete actions). The multiple software deploymentsdescribed in a HOT can consist of deploying middleware and deploying theapplication itself. These deployments can be dependent on previousdeployments, and may change based on various parameters that may requireconfiguration changes to the database.

The end to end installation and deployment process for a VM may includeinstalling a base operating system (OS) image, middleware andapplications, agents and tooling for managed VMs, which can be timeconsuming. When the same deployment and configuration is repeated oneach resource belonging to an auto-scaling group, installation timecontinues to become lengthier. For deployments that require a relativelyfast provisioning, a lengthy installation time can be problematic andinfeasible.

SUMMARY

In an aspect of the invention, a computer-implemented method includes:receiving, by a computing device, a template for creating a virtualmachine (VM) instance; separating, by the computing device, the templateinto a repeated portion and a unique portion; determining, by thecomputing device, whether the repeated portion is stored in a cache;creating, by the computing device and based on determining that therepeated portion is stored in the cache, the VM instance using therepeated portion stored in the cache; completing, by the computingdevice, the unique portion of the VM instance to create a completed VMinstance; and deploying, by the computing device, the completed VMinstance.

In an aspect of the invention, there is a computer program product forexpediting the provisioning of VM instances. The computer programproduct comprises a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya computing device to cause the computing device to: receive a templatefor creating a VM instance; separate the template into a repeatedportion and a unique portion; create the VM instance using an image ofthe repeated portion stored in a cache as a baseline; complete the VMinstance by executing the unique portion of the template; and deploy thecompleted VM instance.

In an aspect of the invention a system comprises: a CPU, a computerreadable memory and a computer readable storage medium associated with acomputing device; program instructions to receive a template forcreating a virtual machine (VM) instance; program instructions toseparate the template into a repeated portion and a unique portion;program instructions to create a repeated VM image by executing codefrom the repeated portion only; program instructions to save therepeated VM image to a cache for use as a baseline in the deployment offuture VM instances having the same repeated portion; programinstructions to complete the VM instance by executing the unique portionof the template; and program instructions to deploy the completed VMinstance. The program instructions are stored on the computer readablestorage medium for execution by the CPU via the computer readablememory.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is described in the detailed description whichfollows, in reference to the noted plurality of drawings by way ofnon-limiting examples of exemplary embodiments of the present invention.

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 shows an overview of an example implementation in accordance withaspects of the present invention.

FIG. 5 shows a block diagram of example components of a VM provisioningserver in accordance with aspects of the present invention.

FIG. 6 shows an example flowchart for fast deployment of a VM instancein accordance with aspects of the present invention.

FIG. 7 shows an example flowchart for separating a template intorepeatable and unique portions in accordance with aspects of the presentinvention.

FIG. 8 shows an example process for patching or modifying a VM instancein accordance with aspects of the present invention.

DETAILED DESCRIPTION

The present invention generally relates to the provisioning of computingresources and, more particularly, to expediting the provisioning andpatching of virtual machine resources in clusters based on cachedrepeated portions of a template.

Provisioning and deploying a VM may be time consuming, as theprovisioning may involve the installation of required operating systems,services, tiers, applications, middleware, software bundles, monitoringagents, etc. For example, the software bundles to be installed may bespecified in a HOT. Each layer in a VM may be managed by differentvendors, which can add further delays to VM deployment. Accordingly,aspects of the present invention may expedite the deployment of new VMsby using cached VM images with commonly used software bundles as abaseline for creating a new VM instance.

More specifically, embodiments herein may separate a template used forprovisioning (e.g., a HOT and/or other type of template) into repeatableand unique portions. The repeatable portions of the template may bestored (e.g., cached) such that the cached repeatable portion may beused to create a new VM instance (e.g., when an auto-scaling group isexpanded to include additional nodes or members). As described herein,repeatable portions may include portions of a template that are generic,non-unique, and/or independent of other factors and instructionsincluded in the template. For example, repeatable portions may includeinstructions with actions to create a VM instance by downloading andinstalling certain applications, middleware, etc. More specifically,repeatable portions may include portions of the template that arenon-unique and are present in multiple different templates and VMdeployments. Unique portions may include particular configurations,preferences, credentials etc., that are specific to a particular VMinstance (e.g., usernames, passwords, hostnames, etc.).

As described herein, when a new VM instance is to be created from atemplate, the template is separated into repeated and unique portions.The repeated portion of the template may be created from a cachedversion of the repeated template, and the unique portion of the templateis then used to complete the creation of the VM instance. In this way,the actions of the repeated portions may not need to be performed fromscratch, thereby significantly reducing provisioning time. In otherwords, a cached VM image with a repeated portion of a template may beused to avoid downloading the same software binaries from repositorieswhen creating a new VM instance, thus saving network bandwidth theinstallation time that may require expanding the binaries and updatingthe numerous configuration files. Aspects of the prevent invention mayalso avoid a situation in which installation failures occur when certainweb resource required for installation may be unavailable. Further,deployment errors are reduced for future repeatable deployments byavoiding potential installation deltas for the repeated portion.

In embodiments, when VM instances from a particular auto-scaling groupare on a same hypervisor, an image of a VM instance may be cached. Whenon different hypervisors, differences between the images of VM instancesmay be transferred to the target hypervisor, thereby speeding updeployment even on different hypervisors.

The present invention may be a system, a method, and/or a computerprogram product at any possible technical detail level of integration.The computer program product may include a computer readable storagemedium (or media) having computer readable program instructions thereonfor causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a nonremovable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and VM provisioning 96.

Referring back to FIG. 1, the program/utility 40 may include one or moreprogram modules 42 that generally carry out the functions and/ormethodologies of embodiments of the invention as described herein (e.g.,such as the functionality provided by VM provisioning 96). Specifically,the program modules 42 may receive a template for creating a VMinstance, separate the template into repeated and unique portions,assign the repeated portion to an auto-scaling group, determine whetherthe repeated portion has been previously cached (e.g., by searching acache or repository), create a new VM using the cached repeated portion,and complete the unique portion of the VM instance. Otherfunctionalities of the program modules 42 are described further hereinsuch that the program modules 42 are not limited to the functionsdescribed above. Moreover, it is noted that some of the modules 42 canbe implemented within the infrastructure shown in FIGS. 1-4. Forexample, the modules 42 may be representative of a VM provisioningserver as shown in FIG. 4.

FIG. 4 shows an example environment in accordance with aspects of thepresent invention. As shown in FIG. 4, environment 400 may include anadministrator device 210, a VM provisioning server 220, a VM server 230,and a network 240. In embodiments, one or more components in environment400 may correspond to one or more components in the cloud computingenvironment of FIG. 2. Also, one or more components in environment 400may include the components of computer system/server 12 of FIG. 1 inorder to carry out the functions described herein.

The administrator device 210 may include one or more computing devicesthat may receive instructions from an administrator to provision a newVM instance (e.g., on the VM server 230). The administrator device 210may include a user interface via which the administrator may inputinformation regarding a VM template (e.g., a HOT) for provisioning thenew VM.

The VM provisioning server 220 may include one or more computing devicesthat may receive a VM template from the administrator device 210,separate the template into repeated and unique portions and obtain arepeated portion from a cache. The VM provisioning server 220 mayfurther complete the unique portion of the template to generate acompleted VM image. The VM provisioning server 220 may provide thecompleted VM image to the VM server 230 to provision/deploy a new VMinstance on the VM server 230.

The VM server 230 may include one or more computing devices that mayhost VMs. In embodiments, the VM server 230 may host VMs associated withdifferent auto-scaling groups. The VM server 230 may host VM instancesthat have been deployed by the VM provisioning server 220.

The network 240 may include network nodes, such as network nodes 10 ofFIG. 2. Additionally, or alternatively, the network 240 may include oneor more wired and/or wireless networks. For example, the network 240 mayinclude a cellular network (e.g., a second generation (2G) network, athird generation (3G) network, a fourth generation (4G) network, a fifthgeneration (5G) network, a long-term evolution (LTE) network, a globalsystem for mobile (GSM) network, a code division multiple access (CDMA)network, an evolution-data optimized (EVDO) network, or the like), apublic land mobile network (PLMN), and/or another network. Additionally,or alternatively, the network 240 may include a local area network(LAN), a wide area network (WAN), a metropolitan network (MAN), thePublic Switched Telephone Network (PSTN), an ad hoc network, a managedInternet Protocol (IP) network, a virtual private network (VPN), anintranet, the Internet, a fiber optic-based network, and/or acombination of these or other types of networks.

As further shown in FIG. 4, the administrator device 210 may provide aVM template to the VM provisioning server 220 (step 1.1). For example,an administrator may input information regarding the template in orderto provision or deploy a new VM instance on the VM server 230. Asdescribed herein, the VM template may be, for example, a HOT and/orother type of template used to deploy a VM instance. At step 1.2, the VMprovisioning server 220 may separate the template into repeated andunique portions. As described herein, the VM provisioning server 220 mayidentify portions of the template that are generic, non-unique, and/orindependent of other factors and instructions included in the template.As described herein, repeatable portions may include portions of atemplate that are generic, non-unique, and/or independent of otherfactors and instructions included in the template. For example,repeatable portions may include instructions with actions to create a VMinstance by downloading and installing certain applications, middleware,etc. More specifically, repeatable portions may include portions of thetemplate that are non-unique and are present in multiple differenttemplates and VM deployments. Unique portions may include particularconfigurations, preferences, credentials etc., that are specific to aparticular VM instance (e.g., usernames, passwords, hostnames, etc.).

At step 1.3, the VM provisioning server 220 may obtain the repeatedportion from a cache or repository storing repeated portions (e.g., bysearching the cache for the repeated portion of the template). At step1.4, the VM provisioning server 220 may complete the unique portion ofthe template, thereby creating a completed VM image or instance thatincludes the cached repeated portion and the completed unique portion.At step 1.5, the VM provisioning server 220 may provision/deploy the VMon the VM server 230. In this way, the completed VM instance is createdusing the cached repeated portion as a “starting point” or base image.As such, the actions of the repeated portions (e.g., downloading andinstalling certain applications, middleware, etc.) will not be needed tobe performed from scratch, thereby significantly reducing provisioningtime.

The quantity of devices and/or networks in the environment 400 is notlimited to what is shown in FIG. 4. In practice, the environment 400 mayinclude additional devices and/or networks; fewer devices and/ornetworks; different devices and/or networks; or differently arrangeddevices and/or networks than illustrated in FIG. 4. Also, in someimplementations, one or more of the devices of the environment 400 mayperform one or more functions described as being performed by anotherone or more of the devices of the environment 400. Devices of theenvironment 400 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

FIG. 5 shows a block diagram of example components of a VM provisioningserver 220 in accordance with aspects of the present invention. As shownin FIG. 5, the VM provisioning server 220 may include a templateseparation module 510, a repeated portion repository 520, a repeatedportion generation module 530, and a unique portion generation module540. In embodiments, the VM provisioning server 220 may includeadditional or fewer components than those shown in FIG. 5. For example,the VM provisioning server 220 may comprise a computer system/server 12of FIG. 1. In embodiments, separate components may be integrated into asingle computing component or module. Additionally, or alternatively, asingle component may be implemented as multiple computing components ormodules.

The template separation module 510 may include a program module (e.g.,program module 42 of FIG. 1) that separates a template into repeated andunique portions. For example, the template separation module 510 mayanalyze the code or text in the template for dependencies. The templateseparation module 510 may determine or “tag” portions of code thatinclude dependencies as “unique” portions. For example, a portion ofcode with a dependency may correspond to a unique portion since the codedepends on a previously identified parameter in the template (e.g., apassword being dependent on a previous portion of code that retrieves auser name). The template separation module 510 may also determine or tagindependent portions of code as “repeated” portions. As described infurther detail with respect to FIG. 7, independent portions and repeatedportions of code may be “provisionally” tagged followed by furtheranalysis and/or user input to confirm or modify the portions as uniqueor repeated.

The repeated portion repository 520 may include a data storage device(e.g., storage system 34 of FIG. 1) that stores cached VM images withdifferent sets of repeated portions. For example, the repeated portionrepository 520 may store an image that includes particular operatingsystems, applications, middleware, etc. preinstalled and/orpreconfigured. Repeated portion repository 520 may store differentcached VM images associated with different auto-scaling groups. Therepeated portion repository 520 may maintain a data structure thatidentifies attributes/metadata of each cached VM image so that thecached VM images can be identified when searched. For example, the datastructure may identify each VM image, the operating systems,applications, middleware, etc. associated with each VM image,auto-scaling groups of each VM image, etc. As described above, the VMimage with repeated portion may be used as a starting point or baseimage for generating a final VM image for deployment/provisioning on theVM server 230.

The repeated portion generation module 530 may include a program module(e.g., program module 42 of FIG. 1) that generates a repeated portionfor a VM image. In embodiments, the repeated portion generation module530 may search the repeated portion in the repeated portion repository520. If a cached VM image that includes the repeated portion is storedby the repeated portion repository 520 (e.g., a cache-hit), the repeatedportion generation module 530 may generate the repeated portion usingthe cached VM image. If a cached VM image is not stored by the repeatedportion repository 520 (e.g., a cache-miss), the repeated portiongeneration module 530 may generate the repeated portion (e.g., fromscratch), and may store a VM image with the repeated portion in therepeated portion repository 520 for future use (e.g., for futuredeployments in which the repeated portion may be used as a basis forgenerating a final VM image).

The unique portion generation module 540 may include a program module(e.g., program module 42 of FIG. 1) that completes a unique portion fora VM image (in which the repeated portion has been first completed). Forexample, the unique portion generation module 540 may execute theinstructions or code in a template that are identified as “unique” afterthe completion of the repeated portion of the VM image. In embodiments,a completed VM image may include a VM image that has been provisioned inaccordance with the code in a template. As discussed above, thegeneration of a completed VM image is substantially faster when a cachedVM image with a completed repeated portion is used as a basis orstarting point for provisioning the VM image.

FIG. 6 shows an example flowchart for fast deployment of a VM instancein accordance with aspects of the present invention. The steps of FIG. 6may be implemented in the environment of FIG. 4, for example, and aredescribed using reference numbers of elements depicted in FIG. 4. Asnoted above, the flowchart illustrates the architecture, functionality,and operation of possible implementations of systems, methods, andcomputer program products according to various embodiments of thepresent invention.

As shown in FIG. 6. process 600 may include receiving a template forcreating a VM instance (step 610). For example, the VM provisioningserver 220 may receive a template for creating a VM instance from theadministrator device 210. In embodiments, the template may include a HOTand/or other type of template that includes information and/orprovisioning instructions for the creation of the VM instance (e.g.,resources to devote to the VM, network communication protocols for theVM, authorized users for the VM, operating systems, applications,middleware to install on the VM, etc.).

Process 600 may further include separating the template into repeatedand unique portions (step 620). For example, as described above withrespect to the template separation module 510, the VM provisioningserver 220 may separate the received template into repeated and uniqueportions. In embodiments, the VM provisioning server 220 may replace theoriginal received template with a “tagged template” containing actionsto create a repeated image and create a unique image. A stack-create maybe issued using the new tagged template. Additional details regardingthe separation of the template are discussed below with respect to theflowchart of FIG. 7. In embodiments, the VM provisioning server 220 maycreate a single repeated portion or multiple different repeatedportions.

Process 600 may also include assigning the repeated portion to anauto-scaling group (step 630). For example, the VM provisioning server220 may assign the repeated portion to a particular auto-scaling group(e.g., a group associated with a particular organization, company,etc.). The VM provisioning server 220 may assign the portion to aparticular auto-scaling group based on information included in thetemplate (e.g., header information identifying the auto-scaling group).

Process 600 may further include determining whether the repeated portionis stored in a cache (step 640). For example, the VM provisioning server220 may determine whether the repeated portion is stored in the cache(e.g., the repeated portion repository 520) by searching the repeatedportion repository 520 with search parameters. Example search parametersmay include the text or code included in the repeated portion, and/or anidentifier of the auto-scaling group.

If, for example, the repeated portion has been previously cached (step640-YES), process 600 may also include creating a new VM instance usingthe cached repeated portion (step 650). For example, as described abovewith respect to the repeated portion generation module 530, the VMprovisioning server 220 may create a new VM instance using the repeatedportion using the cached VM image (e.g., as a baseline for creating thenew VM instance).

Process 600 may further include completing the unique portion of the VMinstance (step 660). For example, as described above with respect to theunique portion generation module 540, the VM provisioning server 220 maycomplete the unique portion of the VM instance by executing theinstructions or code in the unique portion of the template (e.g., theportions in the originally received template that are identified as“unique”). In embodiments, the VM provisioning server 220 may completethe unique portion of the template after the completion of the repeatedportion of the VM image.

Process 600 may also include deploying the VM instance (step 670). Forexample, the VM provisioning server 220 may deploy the VM instance byproviding the completed VM instance to the VM server 230 forimplementation. In this way, the deployment of the VM instance isexpedited since the VM instance was created using a cached repeatedportion as a baseline for VM creation.

If, at step 640, the repeated portion is not previously cached (step640-NO), process 600 may include creating a new VM instance for therepeated portion 680. For example, as described above with respect tothe repeated portion generation module 530, the VM provisioning server220 may create the new VM instance and execute only the code in therepeated portion of the template, thereby creating a VM instance withthe repeated portion. As an example, the VM provisioning server 220 maycreate the new VM instance by obtaining and installing operatingsystems, middleware, applications, etc., as outlined in the repeatedportion of the template.

Process 600 may further include saving the VM instance with the repeatedportion in the cache. For example, the VM provisioning server 220 maystore the VM instance with repeated portion in the cache (e.g., therepeated portion repository 520) for future use (e.g., for futuredeployments in which the repeated portion may be used as a basis forgenerating a final VM image). In embodiments, the VM provisioning server220 may store the VM instance with repeated portion after testing andconfirming that the VM instance is operational. In this way, futuredeployments of VMs having the same repeated portion may be created usingthe cached VM with the repeated portion as a baseline or “startingpoint” (e.g., when expanding an auto-scaling group by adding a new nodeor member). After saving the VM instance with the repeated portion inthe cache, process 600 may continue to steps 660 and 670 as describedabove.

FIG. 7 shows an example flowchart for separating a template intorepeatable and unique portions in accordance with aspects of the presentinvention. The steps of FIG. 7 may be implemented in the environment ofFIG. 4, for example, and are described using reference numbers ofelements depicted in FIG. 4. As noted above, the flowchart illustratesthe architecture, functionality, and operation of possibleimplementations of systems, methods, and computer program productsaccording to various embodiments of the present invention. Inembodiments, the steps of FIG. 7 may include sub-steps of step 620 ofFIG. 6.

As shown in FIG. 7, process 700 may include analyzing template code fordependencies and unique parameters (step 710). For example, the VMprovisioning server 220 may analyze template code for dependencies andunique parameters by parsing the text in the template and searching fordependencies and unique parameters. In embodiments, the VM provisioningserver 220 may perform a static analysis on each line or section oftemplate code to determine whether the section of code includesdependencies and/or unique parameters. As described herein, dependenciesmay include code that requires an input that is obtained based onexecuting another portion of code (e.g., a unique password based on theretrieval of a username). Unique parameters may include code thatidentifies a customization of a setting within an application. Inembodiments, repeated portions of the template may include the portionsof the template that do not include dependencies or unique parameters.

As described herein, a template may include scripts that downloadbinaries (e.g., applications, middleware, etc.), install the binaries,and customize the binaries for specific nodes or parameters. Downloadingand installing the binaries may correspond to the repeated portions ofthe template, whereas customizing the binaries corresponds to the uniqueportion of the template. The VM provisioning server 220 may identifysections of code that are independent of other sections of code (e.g.,code that effectuates the downloading and installing of binaries, butdoes not effectuate customization).

Process 700 may further include determining whether dependencies and/orunique parameters are present (step 720). For example, the VMprovisioning server 220 may determine whether dependencies and/or uniqueparameters are present for each section of analyzed template code. If,for example, dependencies and/or unique parameters are present (step720-YES), process 700 may further include provisionally tagging the codeas unique (step 730). For example, the VM provisioning server 220 mayprovisionally tag the code as unique. If, on the other hand,dependencies and/or unique parameters are not present (step 720-NO),process 700 may further include provisionally tagging the code asrepeated (step 740). For example, the VM provisioning server 220 mayprovisionally tag the code as unique.

Process 700 may also include executing scripts on provisionally taggedcode to update the tags (step 750). For example, the VM provisioningserver 220 may execute scripts on the provisionally tagged code toupdate the tags (e.g., update a provisionally tagged repeated code asunique, or vice versa). In embodiments, the VM provisioning server 220may execute the scripts to correct tags that were initially taggedincorrectly or for unique portions that can be provisioned as repeatedportions (e.g., using a script). As an example, the VM provisioningserver 220 may execute a script to change a provisionally tagged uniquecode to a repeated code when the code includes custom or uniqueparameters (such as custom names for a cell, node, or server). In thisexample, the changing of names for the cell, node, or server can betagged as repeated, and a script can be executed during the provisioningof a VM instance to change the name (e.g., since changing the name usingthe script will be less time consuming than a fresh installation withthe custom name). As another example, a provisionally tagged repeatedcode may be changed to unique based on a script that identifies adependency in an what initially appears to be independent code (e.g., acode in which a current state from a VM is needed).

Process 700 may further include receiving user input to confirm ormodify tags (step 760). For example, the VM provisioning server 220 maypresent the tagged repeated and unique portions to a user oradministrator. The user may review the repeated and unique portions toconfirm the accuracy of the tags. In embodiments, the user may update aportion of code (e.g., to unique from repeated, or vice versa) based onprior knowledge or other factors that indicate that the tag should bechanged. As an example, for a tagged repeated portion, the user maymodify the repeated portion to unique when updates to applications areneeded (e.g., such that provisioning of the VM will download the updatedapplication instead of using a repeated portion with an outdatedapplication).

FIG. 8 shows an example process for patching or modifying a VM instancein accordance with aspects of the present invention. The steps of FIG. 8may be implemented in the environment of FIG. 4, for example, and aredescribed using reference numbers of elements depicted in FIG. 4. Asnoted above, the flowchart illustrates the architecture, functionality,and operation of possible implementations of systems, methods, andcomputer program products according to various embodiments of thepresent invention.

As shown in FIG. 8, process 800 may include receiving a patchinstruction (step 805). For example, the VM provisioning server 220 mayreceive a patch instruction from the administrator device 210. Inembodiments, the patch instruction may identify modifications to make toa particular VM instance (e.g., modifications relating to applications,middleware, operating systems, etc. implemented by the VM instance). Inembodiments, the patch instruction may include text or code thatidentifies the modifications.

Process 800 may further include determining whether the patchinstruction includes a change to the unique portion of the VM instance(step 810). For example, the VM provisioning server 220 may determinewhether the patch instruction includes a change to the unique portion.In embodiments, the VM provisioning server 220 may analyze the patchinstruction and determine whether any changes to a previously determinedunique portion are being made (e.g., as previously determined viaprocess 700). For example, the VM provisioning server 220 may determinethat changes to the unique portion are being made when the patchinstruction includes a modification to a previously determined uniqueportion. In embodiments, idempotent install code may be used todetermine whether the patch instruction includes a change to the uniqueportion of the VM instance.

If for example, the unique portion is not being changed and only therepeated portion is changed (step 810-NO), process 800 may includedraining active requests from the VM instance (step 815). For example,the VM provisioning server 220 may drain active requests from the VMinstance (e.g., by discarding any requests to access or receive servicesfrom the VM instance).

Process 800 may also include installing patches for latest revisions ofchanges (step 820). For example, the VM provisioning server 220 mayinstall the patches in accordance with the patch instruction. Steps 815and 820 may be repeated for each VM instance in the same auto-scalinggroup as the VM instance identified in the patch instruction. In thisway, the repeated portions for all VM instances in the same auto-scalinggroup will be patched.

Process 800 may further include saving the patched repeated image of theVM instance (step 825). For example, the VM provisioning server 220 maysave a repeated image of the VM instance which includes the installedpatches (e.g., in the repeated portion repository 520). The updatedsaved repeated image may be used for the deployment of future VMinstances such that the most up to date patch is implemented in futureVM instances.

If, at step 810, the unique portion is being changed (e.g., in additionto the repeated portion), process 800 may include creating a new VMinstance for the repeated portion (step 830). For example, the VMprovisioning server 220 may create a new VM instance for the repeatedportion as a baseline for which a patched repeated portion will becreated and saved.

Process 800 may further include installing patches for the repeatedportion (step 835). For example, the VM provisioning server 220 mayinstall the patches for the repeated portion of the VM instance inaccordance with the patch instruction. Process 800 may also includesaving the patched repeated image (step 840). For example, the VMprovisioning server 220 may save a repeated image of the VM instancewhich includes the installed patches (e.g., in the repeated portionrepository 520). The updated saved repeated image may be used for thedeployment of future VM instances such that the most up to date patch isimplemented in future VM instances.

Implementations described herein may also be used for containers inaddition to provision of VM instances. For example, techniques describedherein may be used to rearrange RUN commands (e.g., for buildingcontainer images) into repeatable and unique portions.

Process 800 may further include completing the unique portion on the newVM instance (step 845). For example, the VM provisioning server 220 maycomplete the unique portion on the new VM instance in accordance withthe patch instruction. Process 800 may also include draining activerequests from current VM instances and replace with new VM instancescreated from patched image (step 850). For example, for each VM instancein the same auto-scaling group as the VM instance identified in thepatch instruction, the VM provisioning server 220 may drain the activerequests and replace the current VM instances with the new VM instancescreated from the newly saved patched repeated image. In this way, thepatching is completed for all of the VM instances in the auto-scalinggroup. In embodiments, a data cleansing technique may be used whenpatching VM instances (e.g., when customer specific data is present on aVM instance and the image of the instance is used across multipledeployments)

In embodiments, a service provider, such as a Solution Integrator, couldoffer to perform the processes described herein. In this case, theservice provider can create, maintain, deploy, support, etc., thecomputer infrastructure that performs the process steps of the inventionfor one or more customers. These customers may be, for example, anybusiness that uses technology. In return, the service provider canreceive payment from the customer(s) under a subscription and/or feeagreement and/or the service provider can receive payment from the saleof advertising content to one or more third parties.

In still additional embodiments, the invention provides acomputer-implemented method, via a network. In this case, a computerinfrastructure, such as computer system/server 12 (FIG. 1), can beprovided and one or more systems for performing the processes of theinvention can be obtained (e.g., created, purchased, used, modified,etc.) and deployed to the computer infrastructure. To this extent, thedeployment of a system can comprise one or more of: (1) installingprogram code on a computing device, such as computer system/server 12(as shown in FIG. 1), from a computer-readable medium; (2) adding one ormore computing devices to the computer infrastructure; and (3)incorporating and/or modifying one or more existing systems of thecomputer infrastructure to enable the computer infrastructure to performthe processes of the invention.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A computer-implemented method comprising:receiving, by a computing device, a template for creating a virtualmachine (VM) instance, wherein the template includes a repeated portionand a unique portion, and wherein the repeated portion includes aportion of the template that is generic, non-unique, or independent ofother factors and instructions included in the template; separating, bythe computing device, the template into the repeated portion and theunique portion; determining, by the computing device, whether therepeated portion is stored in a cache in the computing device; creating,by the computing device and based on determining that the repeatedportion is stored in the cache, the VM instance using the repeatedportion stored in the cache; completing, by the computing device, theunique portion of the VM instance to create a completed VM instance; anddeploying, by the computing device, the completed VM instance to a VMserver.
 2. The computer-implemented method of claim 1, wherein theunique portion includes particular configurations, preferences,credentials, or other information that is specific to the VM instance.3. The computer-implemented method of claim 1, further comprising:responsive to determining that the repeated portion is not stored in thecache, creating a new VM instance that includes the repeated portion;and saving the VM instance that includes the repeated portion in thecache, wherein completing the unique portion is based on saving the VMinstance that includes the repeated portion in the cache.
 4. Thecomputer-implemented method of claim 1, further comprising assigning therepeated portion to an auto-scaling group, wherein the determiningwhether the repeated portion includes determining whether the repeatedportion is stored in a cache includes an identifier associated with theauto-scaling group.
 5. The computer-implemented method of claim 1,wherein the determining whether the repeated portion is stored in thecache includes searching the cache using search parameters including atleast one from the group consisting of text or code included in therepeated portion and an identifier of the auto-scaling group.
 6. Thecomputer-implemented method of claim 1, wherein the separating thetemplate into the repeated portion and the unique portion includes:analyzing code included in the template for dependencies and uniqueparameters; tagging code with dependencies or unique parameters as theunique portion; and tagging code without dependencies or uniqueparameters as the repeated portion.
 7. The computer-implemented methodof claim 6, further comprising: executing scripts to update the tags;and receiving user input to confirm or modify the tagged code.
 8. Thecomputer-implemented method of claim 1, wherein the template is a HeatOrchestration Template (HOT).
 9. The computer-implemented method ofclaim 1, wherein the deploying the completed VM instance includesproviding the completed VM instance to a virtual machine server thathosts virtual machines.
 10. The computer-implemented method of claim 1,wherein a service provider at least one of creates, maintains, deploysand supports the computing device.
 11. The computer-implemented methodof claim 1, wherein steps of claim 1 are provided by a service provideron a subscription, advertising, and/or fee basis.
 12. Thecomputer-implemented method of claim 1, wherein the computing deviceincludes software provided as a service in a cloud environment.
 13. Thecomputer-implemented method of claim 1, further comprising deploying asystem for expediting the provisioning of VM instances comprisingproviding a computer infrastructure operable to perform the steps ofclaim
 1. 14. A computer program product for expediting the provisioningof virtual machine (VM) instances, the computer program productcomprising a computer readable storage medium having programinstructions embodied therewith, the program instructions executable bya computing device to cause the computing device to: receive a templatefor creating a VM instance, wherein the template includes a repeatedportion and a unique portion, and wherein the repeated portion includesa portion of the template that is generic, non-unique, or independent ofother factors and instructions included in the template; separate thetemplate into the repeated portion and the unique portion; create the VMinstance using an image of the repeated portion stored in a cache in thecomputing device as a baseline; complete the VM instance by executingthe unique portion of the template; and deploy the completed VM instanceto a VM server, wherein the program instructions to separate thetemplate into the repeated portion and the unique portion cause thecomputing device to: analyze code included in the template fordependencies and unique parameters; tag code with dependencies or uniqueparameters as the unique portion; and tag code without dependencies orunique parameters as the repeated portion.
 15. The computer programproduct of claim 14, wherein the template is a Heat OrchestrationTemplate (HOT).
 16. The computer program product of claim 14, whereinthe dependencies include code that requires an input that is obtainedbased on excluding another portion of code and the unique parametersinclude code that identifies a customization of a setting within anapplication.
 17. A system comprising: a CPU, a computer readable memoryand a computer readable storage medium associated with a computingdevice; first program instructions to receive a template for creating avirtual machine (VM) instance, wherein the template includes a repeatedportion and a unique portion, and wherein the repeated portion includesa portion of the template that is generic, non-unique, or independent ofother factors and instructions included in the template; second programinstructions to separate the template into the repeated portion and theunique portion; third program instructions to create a repeated VM imageby executing code from the repeated portion only; fourth programinstructions to save the repeated VM image to a cache for use as abaseline in the deployment of future VM instances having the samerepeated portion; fifth program instructions to complete the VM instanceby executing the unique portion of the template; and sixth programinstructions to deploy the completed VM instance to a VM server, whereinthe program instructions are stored on the computer readable storagemedium for execution by the CPU via the computer readable memory. 18.The system of claim 17, wherein the unique portion includes particularconfigurations, preferences, credentials, or other information that isspecific to the VM instance.
 19. The system of claim 18, furthercomprising: seventh program instructions to receive a patch instructionto patch the VM instance; eighth program instructions to create a new VMinstance for the repeated portion; ninth program instructions to installa patch in accordance with the patch instruction; tenth programinstructions to save the new VM instance as an updated repeated image inthe cache for use as a baseline in the deployment of future VM instanceshaving the same repeated portion; and eleventh program instructions todrain active requests from current VM instances associated with thepatch instruction and replace the current VM instances using the updatedrepeated image.